Define OVOC FQDN and Load Certificate
You need to define the OVOC server with an FQDN that binds to the OVOC Server Public IP address. This FQDN should bind to the OVOC server public IP address and be defined in the public DNS server – each request from every PC connected to the internet should be able to reach the OVOC Public IP address from the FQDN.
| ➢ | Do the following: |
| 1. | Verify that the DNS resolving for the OVOC FQDN is successful, for example Google.com (include example with OVOC Hostname): |
Copy
C:\Users\enterprise1user>nslookup www.google.com
Server: tlc-ovoc.trunkpack.com
Address: 10.1.1.10
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4006:801::2004
172.217.18.36
| 2. | In the OVOC Web, open the OVOC Server Configuration screen (System menu > Administration tab > OVOC Server folder > Configuration) |
OVOC Server Configuration
| 3. | Generate a server certificate with a known Certificate Authority with the OVOC FQDN defined in the CN (or alternatively in SAN) and then import it to the OVOC server (overriding default server certificate) using "Option 3 Import Server Certificates from Certificate Authority (CA)" in the Server Certificates Update menu (see Server Certificates Update |